Dynamic network configuration during device installation

ABSTRACT

One example method of operation may include receiving at a managing device an indication whether a first network device is a known network device, identifying a selected network mode of operation stored in memory of the managing device, and determining whether to cancel the selected network mode of operation based on whether the first network device is a known device.

FIELD OF THE INVENTION

This application relates to a device network configuration and moreparticularly to a dynamic network device configuration during deviceinstallation.

BACKGROUND OF THE INVENTION

Audio product installation requires numerous devices both on the outputor presentation end of the installation and with respect to the controlcenter that is responsible for managing the signals that are sent to theaudio devices.

Enterprise working environments may include a speaker or set of speakerswhich are hung from a suspended ceiling, some speakers may integrate amicrophone into a common housing. The speakers are wired to a controlunit that may include a controller device, an amplifier, wireconfigurations, etc. Conventionally, a network device has two networkports that can have their functionality dynamically configured atruntime. For example, Ethernet ports can be configured to operate as atwo-port Ethernet switch, including, for example, two redundant Ethernetports, or in a media isolation configuration which isolates the mediatraffic from the regular Ethernet control traffic. These portconfigurations can be setup during installation, however, such a setupconfiguration still requires knowledge about the configuration and thedevices by an expert network engineer.

SUMMARY OF THE INVENTION

The present application relates to a method including one or moreoperations of receiving at a managing device an indication whether afirst network device is a known network device, identifying a selectednetwork mode of operation stored in memory of the managing device, anddetermining whether to cancel the selected network mode of operationbased on whether the first network device is a known device.

Another example embodiment may include an apparatus that includes areceiver configured to receive at a managing device an indicationwhether a first network device is a known network device, a processorconfigured to identify a selected network mode of operation stored inmemory of the managing device, and determine whether to cancel theselected network mode of operation based on whether the first networkdevice is a known device.

Still another example embodiment may include a non-transitory computerreadable storage medium configured to store instructions that whenexecuted cause a processor to perform receiving at a managing device anindication whether a first network device is a known network device,identifying a selected network mode of operation stored in memory of themanaging device, and determining whether to cancel the selected networkmode of operation based on whether the first network device is a knowndevice.

Yet another example embodiment may include determining a network mode ofoperation designated by a managing device communicatively coupled to aplurality of network devices, identifying whether one or more of theplurality of network devices are violating one or more compliancemeasures associated with the network mode of operation, determining viathe managing device whether to accept the network configuration orreject the network configuration based on whether one or more of thecompliance measures are violated.

Still yet a further example embodiment may include an apparatus thatincludes a processor configured to determine a network mode of operationdesignated by a managing device communicatively coupled to a pluralityof network devices, identify whether one or more of the plurality ofnetwork devices are violating one or more compliance measures associatedwith the network mode of operation, and determine via the managingdevice whether to accept the network configuration or reject the networkconfiguration based on whether one or more of the compliance measuresare violated.

Still yet another example embodiment may include a non-transitorycomputer readable storage medium configured to store instructions thatwhen executed cause a processor to perform determining a network mode ofoperation designated by a managing device communicatively coupled to aplurality of network devices, identifying whether one or more of theplurality of network devices are violating one or more compliancemeasures associated with the network mode of operation, and determiningvia the managing device whether to accept the network configuration orreject the network configuration based on whether one or more of thecompliance measures are violated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates three different network configurations according toexample embodiments.

FIG. 2 illustrates a detailed example of a daisy-chain networkconfiguration according to example embodiments.

FIG. 3 illustrates a detailed example of a redundant networkconfiguration according to example embodiments.

FIG. 4 illustrates another detailed example of a redundant networkconfiguration according to example embodiments.

FIG. 5 illustrates a detailed example of a fault isolation networkconfiguration according to example embodiments.

FIG. 6 illustrates another detailed example of a fault isolation networkconfiguration according to example embodiments.

FIG. 7 illustrates a detailed example of a daisy-chain configurationnetwork with incorrect wiring according to example embodiments.

FIG. 8 illustrates a detailed flow diagram example process according toexample embodiments.

FIG. 9A illustrates another detailed flow diagram example processaccording to example embodiments.

FIG. 9B illustrates another detailed flow diagram example processaccording to example embodiments.

FIG. 10 illustrates an example system entity configured to perform oneor more operations corresponding to the example embodiments.

DETAILED DESCRIPTION

Example embodiments include a device configuration for a network ofdevices which may include integrated wall or ceiling mountable networkelements, which can provide audio functions, microphone detection, andother sensor, functions, lighting, feedback signals, etc. The device(s)may be part of a network of devices which are centrally controlled andmanaged to offer media services, and which may be controlled by feedbackinformation used to perform beamforming computations which control thespeaker volume of any one or more of the network elements in aparticular environment.

FIG. 1 illustrates three different network configurations according toexample embodiments. The various network configurations are based on thethree different two-port configurations supported by each of the networkdevices. The first example configuration 100 illustrates a daisy-chainport configuration, where a network 100 is connected to a first device106 via a second port, and the device 106 is then connected via a firstport to a second port of another device 104, which is then connected viaa first port to another device 102. The device(s) act as both anendpoint with device specific functionality as well as Ethernet switchfunctionality. With this dual-function configuration, the network canprovide network connectivity to multiple devices without the need of anadditional, dedicated Ethernet switch by connecting additional devicesto one of the ports on the previous device.

Another configuration which may be used in an enterprise networkconfiguration with audio devices may be a redundant configuration 120which redundancy into the network system. In general, this configurationwill isolate the two network ports on a single device 102 from oneanother by installing them to the independent networks 110 and 112 onseparate portions. In yet another example network configuration, anetwork may be setup as a media-isolation mode of operation. In someinstances, an enterprise may not need or desire audio and/or videotraffic on its primary data network. With the media-isolationconfiguration 140, the network device 102 functions as a device with onemedia port (1) to a media network 142 and one control port (2) to acontrol network 144. Typically, this configuration will includeconnecting the ports to different networks to guarantee media traffic isnot sent on the main network.

According to example embodiments, the network device(s) will generallyhave two network RJ-45 ports that can be dynamically configured tooperate differently based on the needs of the application. The portconfigurations may be stored in memory in managing computer device whichis responsible for confirming the network configurations are setupcorrectly according to a set of predefined network port instructions. Ingeneral, there are three main possible modes of operation for thenetwork devices of known devices, and those may include, redundant,daisy-chain and isolation mode. The devices may be known or unknowndevice types and depending on the configurations, the devices may berequired to be known (i.e., familiar manufactured device) in order toconfirm a specific network configuration is correct and if not then theconfiguration may be deemed incorrect.

One example device may be an amplifier. The two ports on the back of theamplifier may act as a two-port Ethernet switch. When the device(s) isconnected directly to the network, the network may provide networkconnectivity to the devices in the chain downstream. This configurationenables configurations to not have to supply a dedicated Ethernet switchto connect with the other devices on the network. Each device in thechain configuration is relying on the device upstream to provide networkconnectivity to the network. The amplifier network device may also have“Network Loop Prevention” logic to avoid incorrect wiring when in adaisy-chain mode of operation. Without this logic, if a network switchwas in a daisy-chain mode and had both its ports plugged directly intoone Ethernet switch or, it could create network loop faults which wouldhang-up the devices and result in connectivity errors. This logic willnot permit this configuration and will generate a fault notificationwith a description of the condition to be created and shared with areporting network device, such as a management server.

The firmware stored in the server and/or lead network device may utilizea Link Layer Discovery Protocol (LLDP) to constantly monitor what isconnected to both network ports. If, at any time, when both ports areconnected and are operational, one of the ports may not be an authorizeddevice, and thus the daisy-chain mode will not be permitted, and a faultwill be generated. If the network is already in a daisy-chain mode ofoperation and this condition of an unknown device occurs, the devicewill force itself into an isolation mode and generate a fault condition.

FIG. 2 illustrates a detailed example of a daisy-chain networkconfiguration according to example embodiments. Referring to FIG. 2, theconfiguration 200 includes a daisy-chain scenario with a network sourceof audio 212, and three network sinks 222, 224 and 226 as additionalnetwork devices. The network audio source 212 includes an interface forinput and output microphones 202 which may be wired and affixed to aceiling. The speakers 204/206/208 (i.e., loudspeakers) which outputaudio at various locations based on the input of the microphones orother audio feeds, may be individually powered and controlled by networkaudio sinks 222/224/226. In this daisy-chain configuration, the cablesare connected from one port to another in an alternating order of anoutput port to an input port from ports 1 to 2. One network audiotransmitting device (i.e., audio source 212) is installed on the networkby having one of its RJ-45 network ports connected to one of the networkports on the first network audio sink 222. Associated analog inputdevices are attached (e.g., microphones) to the source 212.

The first audio network sink's 222 open RJ-45 is connected to one of thesecond network audio sinks 224 RJ-45 ports. Associated analog outputs(speakers) are attached to the sinks. The second network sink's 224 openRJ-45 is connected to one of the third network audio sink's 226 RJ-45ports. Associated analog outputs (speakers) are hooked up. Thedaisy-chain configuration is now setup, and the controlling device nowconfigures the network audio input and network audio output devices toact in daisy-chain mode. This include the network audio source 212transmitting audio and control traffic over its RJ-45 port to the firstnetwork audio sink 222. The first network audio sink 222 receives audioand control traffic on its connection port to the network source andrenders the received audio traffic on its connected analog speakers. Thenetwork audio and control traffic is forwarded on to the second networkaudio sink 224, which receives the audio and control traffic on itsconnected port and renders the received audio on its connected analogspeakers 208. It forwards the received audio and control traffic on tothe third network audio sink 226, which receives the audio traffic fromthe second network audio sink 224 and renders it on its connected analogspeakers 206.

FIG. 3 illustrates a detailed example of a redundant networkconfiguration according to example embodiments. Referring to FIG. 3, theconfiguration 300 includes the same microphones 202 and network source212 device however, the switches 302 and 304 demonstrate two separatenetwork paths used to provide audio and control data to the sink 222 forspeaker output 306. This example represents a redundancy scenario wherea port failure or a switch failure will not affect the outcome of theother port or switch since both are providing the same content to an enddevice 222.

FIG. 4 illustrates another detailed example of a redundant networkconfiguration according to example embodiments. Referring to FIG. 4, theconfiguration 400 provides an audio stream source 412 with variousredundant switches 414 connected to more than one port of the source. Inthis example, there is one network audio transmitting device 412 whichis installed on the network by having both its RJ-45 network portsconnected to redundant ethernet switches 414. One receiving audio device(audio sink 418) is installed by having both its RJ-45 ports connectedto the redundant ethernet switches 414. The RJ-45 network ports on theaudio source 412 and the audio sink 418 may be configured to operate inredundancy mode (e.g., network ports on both devices to change roles ifnecessary). The redundant network audio flows from the audio source tothe audio sink on redundant links 416 removing any single point offailure on the network from dropping audio.

FIG. 5 illustrates a detailed example of a fault isolation networkconfiguration according to example embodiments. Referring to FIG. 5, theconfiguration 500 includes a media isolation scenario with a networkaudio source 212, a network audio sink 504, with inputs form audiotraffic 510 on one link, and all other network traffic 512 on the otherlink. The network data may be enterprise network traffic from networkswitches communicating to a network cloud 522. In operation, the networkmay plug one RJ-45 port on the network audio source to dedicated audiotraffic on the Ethernet switch. The other port is the control port to anenterprise network. Analog inputs may be used to provide microphones202. In a setup configuration, one RJ-45 jack is hooked up to a networkaudio sink for an audio traffic only Ethernet switch and the other RJ-45jack to the enterprise network 522 and switches 502. Analog outputdevices (speakers 306) are also setup to the sink 504. The devices aresetup to isolate audio/video data from the control network data. Thenetwork audio source 212 and network audio sink 504 may have theirnetwork ports configured to operate in isolation mode. Audio data onlyis sent out the provisioned audio port, and all control data istransmitted over the control only port, thus isolating the audio/videodata from the normal network traffic.

FIG. 6 illustrates another detailed example of a fault isolation networkconfiguration according to example embodiments. In FIG. 6, theconfiguration 600 demonstrates how the enterprise network may includevarious devices 610, such as enterprise computers 604 and file server606, etc., all of which operate on the enterprise network portion of thesink 612. The other port of the device is connected to a dedicatedaudio/video network 620 with an audio stream source 602.

FIG. 7 illustrates a detailed example of a daisy-chain configurationnetwork with incorrect wiring according to example embodiments.Referring to FIG. 7, the configuration 700 provides an example ofactions taken when the network management application and device detectan incorrect setup. In this daisy-chain induced network loop scenario, anetwork engineer may incorrectly wire the device so that the daisy-chainmode can lead to accidental network loops. If the installers intent is aredundant connection but they accidently select daisy-chain or themanagement device is setup to identify daisy-chain, but theconfiguration is wired as a redundant connection, the accidental networkloop condition may occur causing packet storms and network errors. Thismay be detected, and an error may occur so that an error notification iscreated and sent to the management device (not shown).

FIG. 8 illustrates a detailed flow diagram example process according toexample embodiments. Referring to FIG. 8, the configuration 800 providesa method of operation where the managing device can identify a networkconfiguration, compare the configuration to an expected configuration,and determine whether to create an error notification when theconfiguration fails or is determined to be incorrect.

In general, the device may be identified 802 for a particular hardwareprofile, such as a hardware address or other indication that indicateswhether the device is known 804 or unknown. When the device is known isin communication with the managing device, the network configurationwill include the known device providing an indicator of acknowledgementsuch as a hardware ID, a flag, a code, etc., in the form of a datapacket or message. The process is completed for that device and otherdevices may be checked in subsequent operations for compliance anddetermine whether the network configuration setup in the managing deviceis correct. Next, in the case of a daisy-chain mode of operation, if thenetwork is not in daisy-chain mode, the process may be deemed correctsince the network failures occur in a daisy-chain mode of operation vs.a redundancy mode and/or isolation mode of operation. If the daisy-chainmode of operation is selected 806, as stored in the managing devicememory, then the lack of known devices may cause an automaticdaisy-chain error indication to occur. This may cause the daisy-chainoperation to be cancelled 808. When the operation is cancelled themanaging device may create a wiring error notification 810.

For a redundant network mode of operation, the network audio source maybe plugged in so that its RJ-45 ports are plugged in to two different(redundant) Ethernet switches and all analog inputs (microphones) areplugged in as well. The network audio sink is wired so that both itsRJ-45 network ports are plugged in to the same switch, and all analogoutputs (speakers) are plugged in as well. In this case, when a networkoperator (incorrectly) puts the network audio sink into a daisy-chainmode of connections, a network loop may occur. The loop preventionalgorithm of the application of the managing device may detect thenetwork loop condition and reject the daisy-chain mode request, causinga fault indication notifying the operator that an incorrect wiringcondition exists.

FIG. 9A illustrates another detailed flow diagram example processaccording to example embodiments. Referring to FIG. 9A, the examplemethod 900 includes a receiving at a managing device an indicationwhether a first network device is a known network device 912,identifying a selected network mode of operation stored in memory of themanaging device 914, and determining whether to cancel the selectednetwork mode of operation based on whether the first network device is aknown device 916. In one example, the selected network mode of operationis a daisy-chain network mode of operation. The daisy-chain network modeof operation includes one port on the first network device beingconnected to one port on a second network device. The first networkdevice is communicatively coupled to the managing device via oneadditional port on the first network device, and a second port on thesecond network device is connected to one or more additional networkdevices. The method also includes identifying the first network deviceis not a known device and cancelling the selected network mode ofoperation, and creating an error notification indicating thecancellation.

FIG. 9B illustrates another detailed flow diagram example processaccording to example embodiments. Another example method of operationincludes a method 950 that includes determining a network mode ofoperation designated by a managing device communicatively coupled to aplurality of network devices 952, identifying whether one or more of theplurality of network devices are violating one or more compliancemeasures associated with the network mode of operation 954, anddetermining via the managing device whether to accept the networkconfiguration or reject the network configuration based on whether oneor more of the compliance measures are violated 956. The compliancemeasures may include one or more ports of a network device beingconnected to one or more ports of another network device, and one ormore ports of the another device being connected to one or more ports ofan additional device, or, two or more ports of the network device beingconnected to two respective separate ports of the another network deviceand the additional network device. In this example, the network mode ofoperation is one or more of a daisy-chain network mode of operation, aredundant network mode of operation and an isolated network mode ofoperation depending on the port configurations and the known devicesbeing identified.

The daisy chain network mode of operation requires two or more ports ofat least one of the plurality of network devices being connected to twodifferent network devices. The redundant network mode of operationrequires two or more ports of a network device being connected to twodifferent network devices which both connect to a same network device.The determined network mode of operation is violated when one or more ofthe plurality of network devices violates one or more of the compliancemeasures. When the network mode of operation is violated, the selectednetwork mode of operation is cancelled and an error notificationindicating the cancellation is created.

The above embodiments may be implemented in hardware, in a computerprogram executed by a processor, in firmware, or in a combination of theabove. A computer program may be embodied on a computer readable medium,such as a storage medium. For example, a computer program may reside inrandom access memory (“RAM”), flash memory, read-only memory (“ROM”),erasable programmable read-only memory (“EPROM”), electrically erasableprogrammable read-only memory (“EEPROM”), registers, hard disk, aremovable disk, a compact disk read-only memory (“CD-ROM”), or any otherform of storage medium known in the art.

An exemplary storage medium may be coupled to the processor such thatthe processor may read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anapplication specific integrated circuit (“ASIC”). In the alternative,the processor and the storage medium may reside as discrete components.For example, FIG. 10 illustrates an example computer system architecture1000, which may represent or be integrated in any of the above-describedcomponents, etc.

FIG. 10 is not intended to suggest any limitation as to the scope of useor functionality of embodiments of the application described herein.Regardless, the computing node 1000 is capable of being implementedand/or performing any of the functionality set forth herein.

In computing node 1000 there is a computer system/server 1002, which isoperational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 1002 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 1002 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 1002 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 10, computer system/server 1002 in cloud computing node1000 is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 1002 may include, but are notlimited to, one or more processors or processing units 1004, a systemmemory 1006, and a bus that couples various system components includingsystem memory 1006 to processor 1004.

The bus represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Computer system/server 1002 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 1002, and it includes both volatileand non-volatile media, removable and non-removable media. System memory1006, in one embodiment, implements the flow diagrams of the otherfigures. The system memory 1006 can include computer system readablemedia in the form of volatile memory, such as random-access memory (RAM)1010 and/or cache memory 1012. Computer system/server 1002 may furtherinclude other removable/non-removable, volatile/non-volatile computersystem storage media. By way of example only, storage system 1014 can beprovided for reading from and writing to a non-removable, non-volatilemagnetic media (not shown and typically called a “hard drive”). Althoughnot shown, a magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to thebus by one or more data media interfaces. As will be further depictedand described below, memory 1006 may include at least one programproduct having a set (e.g., at least one) of program modules that areconfigured to carry out the functions of various embodiments of theapplication.

Program/utility 1016, having a set (at least one) of program modules1018, may be stored in memory 1006 by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystem, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. Program modules 1018 generally carry outthe functions and/or methodologies of various embodiments of theapplication as described herein.

As will be appreciated by one skilled in the art, aspects of the presentapplication may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present application may take theform of an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present application may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Computer system/server 1002 may also communicate with one or moreexternal devices 1020 such as a keyboard, a pointing device, a display1022, etc.; one or more devices that enable a user to interact withcomputer system/server 1002; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 1002 to communicate withone or more other computing devices. Such communication can occur viaI/O interfaces 1024. Still yet, computer system/server 1002 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via a network adapter. The network adapter communicateswith the other components of computer system/server 1002 via a bus. Itshould be understood that although not shown, other hardware and/orsoftware components could be used in conjunction with computersystem/server 1002. Examples, include, but are not limited to:microcode, device drivers, redundant processing units, external diskdrive arrays, RAID systems, tape drives, and data archival storagesystems, etc.

Although an exemplary embodiment of at least one of a system, method,and non-transitory computer readable medium has been illustrated in theaccompanied drawings and described in the foregoing detaileddescription, it will be understood that the application is not limitedto the embodiments disclosed, but is capable of numerous rearrangements,modifications, and substitutions as set forth and defined by thefollowing claims. For example, the capabilities of the system of thevarious figures can be performed by one or more of the modules orcomponents described herein or in a distributed architecture and mayinclude a transmitter, receiver or pair of both. For example, all orpart of the functionality performed by the individual modules, may beperformed by one or more of these modules. Further, the functionalitydescribed herein may be performed at various times and in relation tovarious events, internal or external to the modules or components. Also,the information sent between various modules can be sent between themodules via at least one of: a data network, the Internet, a voicenetwork, an Internet Protocol network, a wireless device, a wired deviceand/or via plurality of protocols. Also, the messages sent or receivedby any of the modules may be sent or received directly and/or via one ormore of the other modules.

One skilled in the art will appreciate that a “system” could be embodiedas a personal computer, a server, a console, a personal digitalassistant (PDA), a cell phone, a tablet computing device, a smartphoneor any other suitable computing device, or combination of devices.Presenting the above-described functions as being performed by a“system” is not intended to limit the scope of the present applicationin any way but is intended to provide one example of many embodiments.Indeed, methods, systems and apparatuses disclosed herein may beimplemented in localized and distributed forms consistent with computingtechnology.

It should be noted that some of the system features described in thisspecification have been presented as modules, in order to moreparticularly emphasize their implementation independence. For example, amodule may be implemented as a hardware circuit comprising custom verylarge-scale integration (VLSI) circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field programmable gate arrays, programmable arraylogic, programmable logic devices, graphics processing units, or thelike.

A module may also be at least partially implemented in software forexecution by various types of processors. An identified unit ofexecutable code may, for instance, comprise one or more physical orlogical blocks of computer instructions that may, for instance, beorganized as an object, procedure, or function. Nevertheless, theexecutables of an identified module need not be physically locatedtogether but may comprise disparate instructions stored in differentlocations which, when joined logically together, comprise the module andachieve the stated purpose for the module. Further, modules may bestored on a computer-readable medium, which may be, for instance, a harddisk drive, flash device, random access memory (RAM), tape, or any othersuch medium used to store data.

Indeed, a module of executable code could be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within modules and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork.

It will be readily understood that the components of the application, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations.Thus, the detailed description of the embodiments is not intended tolimit the scope of the application as claimed but is merelyrepresentative of selected embodiments of the application.

One having ordinary skill in the art will readily understand that theabove may be practiced with steps in a different order, and/or withhardware elements in configurations that are different than those whichare disclosed. Therefore, although the application has been describedbased upon these preferred embodiments, it would be apparent to those ofskill in the art that certain modifications, variations, and alternativeconstructions would be apparent.

While preferred embodiments of the present application have beendescribed, it is to be understood that the embodiments described areillustrative only and the scope of the application is to be definedsolely by the appended claims when considered with a full range ofequivalents and modifications (e.g., protocols, hardware devices,software platforms etc.) thereto.

What is claimed is:
 1. A method comprising: identifying a daisy-chainmode as a selected network mode of operation stored in memory of amanaging device wherein the daisy-chain mode comprises one port on afirst network device being connected to one port on a second networkdevice and another port of the first network device being connected tothe managing device; and cancelling the daisy-chain network mode ofoperation when the first network device is not a known device.
 2. Themethod of claim 1, comprising receiving at the managing device anindication whether the first network device is a known device.
 3. Themethod of claim 1, comprising determining whether to cancel the selectednetwork mode of operation based on whether the first network device is aknown device.
 4. The method of claim 1, wherein a second port on thesecond network device is connected to one or more additional networkdevices.
 5. The method of claim 1, comprising identifying the firstnetwork device is not a known device.
 6. The method of claim 5,comprising cancelling the selected network mode of operation.
 7. Themethod of claim 6, comprising creating an error notification indicatingthe cancellation.
 8. A system comprising: a processor and memorycommunicably coupled to the processor, wherein the processor isconfigured to perform: identify a daisy-chain mode as a selected networkmode of operation stored in memory of a managing device wherein thedaisy-chain mode comprises one port on a first network device connectedto one port on a second network device and another port of the firstnetwork device are connected to the managing device; and cancel thedaisy-chain network mode of operation when the first network device isnot a known device.
 9. The system of claim 8, comprising receive at themanaging device an indication whether the first network device is aknown device.
 10. The system of claim 8, comprising determine whether tocancel the selected network mode of operation based on whether the firstnetwork device is a known device.
 11. The system of claim 8, wherein asecond port on the second network device is connected to one or moreadditional network devices.
 12. The system of claim 8, comprising thatidentifies the first network device is not a known device.
 13. Thesystem of claim 12, comprising cancel the selected network mode ofoperation.
 14. The system of claim 13, comprising create an errornotification that indicates the cancellation.
 15. A non-transitorycomputer readable medium comprising instructions, that when read by aprocessor, cause the processor to perform: identifying a daisy-chainmode as a selected network mode of operation stored in memory of amanaging device wherein the daisy-chain mode comprises one port on afirst network device being connected to one port on a second networkdevice and another port of the first network device being connected tothe managing device; and cancelling the daisy-chain network mode ofoperation when the first network device is not a known device.
 16. Thenon-transitory computer readable medium of claim 15, comprisingreceiving at the managing device an indication whether the first networkdevice is a known device.
 17. The non-transitory computer readablemedium of claim 15, comprising determining whether to cancel theselected network mode of operation based on whether the first networkdevice is a known device.
 18. The non-transitory computer readablemedium of claim 15, wherein a second port on the second network deviceis connected to one or more additional network devices.
 19. Thenon-transitory computer readable medium of claim 18, comprisingcancelling the selected network mode of operation.
 20. Thenon-transitory computer readable medium of claim 19, comprising creatingan error notification indicating the cancellation.